home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solutions.solon.com (Peter Seebach)
- Newsgroups: comp.lang.pl1,comp.lang.c
- Subject: Re: PL/I and C
- Date: 29 Feb 1996 12:08:36 -0600
- Organization: Usenet Fact Police (Undercover)
- Message-ID: <4h4q34$bjh@solutions.solon.com>
- References: <4gh5ru$eng@goanna.cs.rmit.EDU.AU> <TANMOY.96Feb23212936@qcd.lanl.gov> <4h0gn2$mnk@wizvax.wizvax.net> <TANMOY.96Feb28084301@qcd.lanl.gov>
- NNTP-Posting-Host: solutions.solon.com
-
- In article <TANMOY.96Feb28084301@qcd.lanl.gov>,
- Tanmoy Bhattacharya <tanmoy@qcd.lanl.gov> wrote:
- >RS: Last I knew the size of an int was compiler dependent.
-
- >Last I knew, every type (other than bit field) in C had a `compiler
- >dependent' size.
-
- If you mean in terms of sizeof(), you are wrong - char, signed char, and
- unsigned char have compiler independant size.
-
- If you mean in terms of real storage, you are wrong - bitfields may vary in
- real size, because they may be padded. (I think.) Consider
- struct foo {
- int bar:15, baz:15, quux:15;
- };
-
- >I fail to see what this has to do with the validity of arrays in
- >struct.
-
- Well, that's comforting, I can't tell either.
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-